Release 10.1A: OpenEdge Development:
ADM and SmartObjects

Reviewing conversion results

This section describes the specific changes that occur when converting ADM1 SmartObjects to ADM2 SmartObjects. The changes it describes include ADM1-to-ADM2 SmartObject conversions, specific ADM file-conversion changes, and additional conversion changes.

Table B–5 lists the ADM1-to-ADM2 9 SmartObject file conversions the conversion utility tries to perform.

Table B–5: ADM1 to ADM2 SmartObject conversions 

ADM1 SmartObject	Corresponding ADM2 SmartObject
ADM1 SmartWindow	ADM2 SmartWindow
ADM1 SmartDialog	ADM2 SmartDialog
ADM1 SmartFrame	ADM2 SmartFrame
ADM1 SmartBrowser	ADM2 SmartDataBrowser
ADM1 SmartQuery	ADM2 SmartDataObject
ADM1 SmartViewer	ADM2 SmartDataViewer

Table B–6 identifies specific ADM1-to-ADM2 file conversion changes.

Table B–6: Specific file conversion changes 

For this element...	All...	Are...
RUN DISPATCH	RUN dispatch [ IN hdl ] ( [ INPUT ] ’proc’ ).	Converted to: RUN proc [ IN hdl ] Or, if it is a local copy of itself: RUN SUPER
RUN NOTIFY	RUN notify [ IN hdl ] ( [ INPUT ] ’proc’ ).	Converted to: PUBLISH ’proc’ [ FROM hdl ]
GET-ATTRIBUTE	RUN get-attribute [ IN hdl ] ( [ INPUT ] ) ’attr’). var=RETURN-VALUE.	Converted to: var=[hdl:]getpropname ( ).
SET-ATTRIBUTE-LIST	RUN set-attribute-list ( [ INPUT ] ’attr1=val1, attr2=val2, ... ’ ).	Replaced by: {setpropname1 val1} {setpropname2 val2}

A variable that contains a list is not converted. You must write your own get and set property functions for any customized attributes.

Some common ADM1 attribute names automatically are converted to the corresponding ADM2 property names (for example, Current-Page to Current Page), based on entries in the file protools/v89names.dat. You can extend this list as described in the "Customizing the conversion utility" section.

This list identifies operations that the conversion utility performs for all converted files:

Removes the following prefixes from procedures and procedure dispatches:
adm-.
local-.
broker-.
Any custom prefix defined in protools/convt89.p variable cCustomPrefix.
Replaces all strings found in the ++ Old Name column of protools/v89names.dat file with the corresponding string in the ++ New Name column.
Removes all procedures and attribute references found in the protools/v89names.dat file ++ Remove List.
Replaces local-exit procedures with exitObject procedures.
Edits the ADM-SUPPORTED-LINKS preprocessor to reflect the Version 9 link types.
When TABLES-IN-QUERY-... and ENABLED-TABLE-IN-QUERY... have more than one table, generates SECOND-TABLE-IN-QUERY-..., SECOND-ENABLED-TABLE-IN-QUERY-... preprocessors up to the TENTH-TABLE... .
When converting a SmartViewer or SmartBrowser, generates an include file with a reasonably appropriate set of field definitions for the ADM2 SmartDataObject RowObject temp-table and flagged with an &MESSAGE statement to indicate that it should be replaced with an include file from an appropriate SmartDataObject.
Removes external table definitions.
If a procedure is dispatched inside of an instance of itself (for example, dispatching abc inside local-abc), converts this to RUN SUPER syntax.
Converts Init-Object procedures to constructObject procedures. This includes the conversions of variable attributes to their ADM2 names. For example, Layout becomes ObjectLayout, Edge-Pixels becomes EdgePixels, SmartPanelType becomes PanelType, Right-to-Left becomes RightToLeft, and so on.
Converts the procedure settings to the ADM2 format. These new formats are required by the AppBuilder to re-establish the correct state when reading the .w file.
Creates appropriate field definitions in the Runtime Attribute Settings when converting a Version 8 SmartQuery to an ADM2 SmartDataObject.
Converts states based on the values of the cStateVals and cStateProps variables in the _convt89.p procedure.
Removes the entire Method Library section and replaces it with the appropriate Version 9 include files based on the type of object to which it is being converted. The utility determines this by reading the ADM1 template type found in the Definitions section, as shown below:

Description: from VIEWER.W - Template for SmartViewer Objects

If the utility does not find this line, the SmartObject cannot be properly converted. Be sure to restore the line in the Definitions section before attempting the conversion.

If a SmartObject has ADM1 custom method libraries you need to retain, you need to re-insert them after the conversion. Generally, you have to convert these custom method libraries, as they might not work with ADM2.